Welcome to Aldus Fetch! This ReadMe file supplements the booklet, Aldus Fetch Getting Started, with additional technical details and late-breaking product information that was not available when the booklet went to press.
Please read this file carefully — especially the section about installing — before you begin working with Fetch. We also recommend that you print a copy of the file and keep it with Aldus Fetch Getting Started.
The Aldus Fetch Trial Version is the same as the retail version, with the following exceptions:
• You do not need a serial number to use the Trial Version.
• Each Trial Version catalog can contain a maximum of 50 items. (A catalog created using the retail version can contain more than 100,000 items.)
Use the Trial Version to explore the capabilities of Aldus Fetch and discover all that it can do for you. When you’re ready to order the full retail product — with which you receive a full set of printed and online documentation, technical support and customer services, and mailings about future releases — use the enclosed order form or call Aldus Customer Services for order information. In the United States and Canada, call 1-206-628-2320. Elsewhere, contact your local Aldus dealer or distributor.
Please read this file carefully before you begin working with Aldus Fetch 1.2. We recommend that you print a copy of this file and keep it with your Aldus Fetch Getting Started.
• The minimum amount of memory you should allocate to Fetch is 1900 KB. Running Fetch with this amount of memory or less, however, may cause problems with some large files that require more memory.
• Scrapbook 7.1.2 is installed only on System 7. The Scrapbook file itself is left unchanged.
• For System 7, QuickTime 1.6.1 is automatically installed in your Extensions folder. If you have another version of QuickTime in another location, you should remove it so you don't receive an error when restarting your Macintosh.
TRANSFERRING IMAGES INTO PAGEMAKER 5.0 DOCUMENTS
• By using the Copy Reference command in Fetch, you can transfer images cataloged in Fetch into the PageMaker 5.0 Library Palette. See the PageMaker 5.0 documentation for information on how to use the Library Palette. PageMaker 5.0 lets you transfer the following file types from Fetch into its Library Palette:
edtp (PICT-based Edition)
edtt (text-based Edition)
EPSF (Encapsulated Postscript)
PCDI (Kodak photo CD image)
PICT
PNTG (MacPaint file)
TIFF
FILE TYPES
• For the compressed sound file types of AIFC and FSSD, you can catalog and play 3:1 and 6:1 MACE compression, but you cannot play 4:1 or 8:1 MacroMind compression (an error message appears).
• To prevent Fetch from cataloging QuickTime movies with small thumbnails, uncheck the “Extract Thumbnail” option in the Add/Update dialog box before cataloging. In this way, Fetch creates a normal sized thumbnail rather than using the smaller thumbnail that QuickTime creates.
• Files wider than 4000 pixels can be cataloged, but cannot be previewed.
• Because few applications directly decompress Disk Doubled files, you may not be able to use the Edit Original, Send Reference, or Copy Reference commands on a Disk Doubled file.
• Applications that you catalog with Fetch have the file type APPL.
• Fetch 1.2 supports the following TIFF formats:
Bit map:
Uncompressed
Word-boundaried Uncompressed
Huffman CCITT-1D Compressed
Packbits Compressed
LZW Compressed (w & w/o Differencing)
Gray scale:
4-bit Uncompressed
8-bit Uncompressed
4-bit LZW Compressed (w & w/o Differencing)
8-bit LZW Compressed (w & w/o Differencing)
4-bit Thunder Scan Compressed
Palette Color:
4-bit Uncompressed
8-bit Uncompressed
4-bit LZW Compressed (w & w/o Differencing)
8-bit LZW Compressed (w & w/o Differencing)
RGB Color:
24-bit Uncompressed
24-bit LZW Compressed (w & w/o Differencing)
6-5-5 16-bit Uncompressed
CMYK Color:
8-8-8-8 CMYK Uncompressed
8-8-8-8 CMYK LZW Compressed (w & w/o Differencing)
• Fetch 1.2 does not support the following TIFF extensions:
• When printing thumbnails on a QMS 100/30 printer, you need to use the LW 8.0 driver to get the correct printing area.
• When printing thumbnails on a QMS 230 printer, you may find that the printing area is incorrect with LW 7.1.x and 8.0 drivers. The best result is with the 8.0 driver in the landscape setting.
• To avoid an incorrect printing area when printing on Tektronix IIIPXi or SDX printers, use the Phaser paper settings (when provided) in the Page Setup dialog box.
• If errors appear when printing thumbnails with the LW 7.1.x drivers, try using the 8.0 driver.
• When you print thumbnails with the Graphic Smoothing option turned on, horizontal white lines may appear on the printed thumbnails.
• If you are printing very large images with the Print Actual Images option turned on, then you may need to allocate more memory to Fetch.
MISCELLANEOUS
• If you want to add Aldus FreeHand (3.11 and later) and PageMaker (5.0 and later) files to a Fetch catalog, you need to set the correct options before saving the file. Before saving the file in FreeHand or PageMaker, make sure that the “Include Fetch Preview” option is checked in FreeHand's “Preferences” dialog box and that the “Save Preview” option is checked in PageMaker's “Save As...” dialog box. Otherwise, the thumbnails and previews will not appear in Fetch.
• The Macintosh SE computer does not support QuickTime. Therefore, movies and sounds cannot be viewed with Fetch on Macintosh SEs. Instead, a Fetch Error thumbnail appears when you catalog movies and sounds with an SE.
• If you are importing a catalog exported from Multi-Ad Search 1.0 (see the Tip on page 68 of the Aldus Fetch User Guide), make sure that the volume referenced by the catalog is mounted.
• If you are running Fetch on a Macintosh with a Radius Rocket card and you have 8MB or less of memory, Fetch can hang when cataloging items. Increase Fetch's memory allocation to avoid this situation.
• Files copied to a Novell server assume the date and time of the transfer as their creation date and time. Since Fetch uses a file's creation date for identification, it is recommended that you copy files to the Novell server before you catalog them in Fetch. Otherwise, because the creation dates change after copying, Fetch will see the files as new files when you attempt to update the catalog with their new location and Fetch will duplicate those items in the catalog.
• In the File Search dialog box that appears when you press the “Continue...” button in the Add/Update dialog box, the Preview area may not preview the selected file, even though you can preview the file (and view its thumbnail) once it has been cataloged. If you use the Create button, however, to create a preview, QuickTime adds a pnot resource to the file, modifying the file and creating a thumbnail that is smaller than the thumbnail created when you catalog the file. To avoid modifying the original file and having two different-sized thumbnails for the same file, it is recommended that you do not use the Create button.
In addition, when choosing to catalog files that have been compressed using DiskDoubler or when choosing to catalog aliases for volumes or folders, the Open button in this dialog box may change to a Convert button. The Convert button acts as the Open button. When you press the Convert button, the files, volumes, or folders will be cataloged normally.
• Make sure to update a catalog before purging it. Because the purge command checks for original files, if you have not updated an item and that item's file has been moved or renamed, the item will appear on the purge list. Updating before purging avoids unintentional deletion of files.
• With multiple users working in the same catalog, an alert “Cannot delete while other users are making changes” appears when two or more users are trying to make simultaneous changes to the catalog. If one user is trying to delete an item and clicks OK on the alert, the item disappears from the catalog, but is not deleted. Clicking “All” in the Search menu makes the item visible again.
• If you add a keyword that contains punctuation, the keyword appears twice, once with the punctuation, and once without. For example, if you add the keyword DOG!, you will see DOG and DOG! in the keyword list.
Some additional guidelines follow:
-- Installing Aldus Fetch
As the size of the files you work with increases and the complexity of your task within Fetch grows, you may find that you want to allocate more memory to Fetch than is recommended in the Aldus Fetch Getting Started. Here are some guidelines for the amount of memory you will need:
- You need at least 1.9 MB to run Fetch (regardless of the file or catalog size).
- For TIFFs and other scanned images, you will need enough memory to accommodate the base minimum of 1.5 MB plus twice the size of the uncompressed file being cataloged. For instance, cataloging a 4 MB TIFF requires 9.5 MB of memory (1.9 MB for Fetch, plus 8 MB for the TIFF).
If there is not enough RAM to complete the cataloging of a file, Fetch attempts to use the disk space available on the boot drive. Fetch indicates this by switching the cursor from a spinning bone to a rotating SCSI icon. If there is not enough disk space to complete the catalog process, you will see a “disk error” message instead of the thumbnail in the Fetch catalog.
If you are using DiskDoubler to decompress files during cataloging, you should be aware that:
- DiskDoubler may need to access the unused disk space on your boot drive. When decompressing a file, DiskDoubler first uses the RAM allocated to it. If it runs out of RAM, it tries to complete the decompression using any available disk space. Successful decompression may require disk space equal to that of the decompressed file. (NOTE: As mentioned in the preceding paragraph, Fetch may also need disk space to complete the catalog process. If this happens, you will need enough disk space to complete both the decompression and cataloging processes.)
- Cataloging on a disk that is locked or full could cause DiskDoubler problems. Recent versions of DiskDoubler write to a scratch space on the system hard drive. If this drive is locked or full, DiskDoubler will not be able to complete the decompression. Older DiskDoubler versions do not write to this scratch space and do not experience this problem.
--Starting Aldus Fetch and opening a catalog
If you start Fetch when the Clipboard contains a very large text or PICT object (more than 32K for text or more than 600K for a PICT) and Fetch needs more memory to start, it will clear the Clipboard but display a message to tell you it has done so. Two other situations can also require Fetch to clear the Clipboard: when you copy a large item to the Clipboard in Fetch, switch out of Fetch, perform a memory-intensive operation, and then switch back to Fetch; or when you switch to another application, fill the Clipboard from there with a very large object, and then switch back to Fetch.
Force-quitting from Fetch (by pressing Command + Option + Esc only if you are running System 7) leaves the open catalog in an undefined state. In this case, restarting your computer before restarting Fetch will help to avoid problems.
-- Searching through a catalog
When performing a complex search, the conjunction “or” indicates a break in the search criteria. For example, the search:
File Type TIFF
and
Keyword matches blue
or
Keyword matches green
results in Fetch searching for all TIFF images that have the keyword blue and ALL files that have the keyword green. To search for only TIFF images that have either the keyword blue or green, the search should be as follows:
File Type TIFF
and
Keyword matches blue
or
File Type TIFF
and
Keyword matches green
-- Viewing search results
In the Gallery and Pasteboard windows, you can use the “By…” commands on the View menu to organize the items in the window the way you want them. Note, however, that although “By File Type” organizes items alphabetically by the file type of the source item, the order is case-sensitive. Thus, file types that begin with a capital letter appear first, followed by file types that begin with a lowercase letter. Within each file type, items are shown in the order that Fetch cataloged them.
-- Previewing an item
The default memory allocation for Fetch (2400K) is based on average file sizes and systems. Because the memory required to preview a file is based on its pre-compressed file size, you might want to increase the memory allocation if you routinely preview large files. Previewing very large images may require an allocation of 3 MB or higher.
When you preview (or choose “Get Info” for) an item whose source file is on a removable medium that is mounted remotely (for example, a CD-ROM or a Bernoulli drive on someone else’s computer), Fetch sometimes prompts you anyway to mount the volume. However, when you click the Cancel button in the alert, the command completes as you would expect.
When you have opened the destination folder in the “Move Original” or “Copy Original” dialog box, press the “Folder” button to complete the process. The “Folder” button acts like a “Save” button and will move or copy the selected item’s source file to the opened folder.
-- Using an item in another document
When you send an item reference to Multi-Ad Creator, an inconsistency can occur that is similar to the one described in the “Previewing an item” section of this ReadMe. If you select an item whose source file is on a remotely mounted volume and choose “Send Reference…,” the item does not appear on the files palette in Multi-Ad Creator. If you are trying to send the reference to your own computer, use “Copy Reference” instead. If you are trying to send the reference to another computer, choose “Add/Update Items…” from the Admin menu, then choose “Update Unconditionally” as the “Modification Method” option. Update the items that you want to send to Multi-Ad Creator, then try “Send Reference…” again.
-- Creating a new catalog, Updating a catalog
If you have multiple Novell volumes with the same name, Fetch will treat them as if they were all one volume. To avoid this situation, make sure that all Novell volumes have unique names. Although Fetch does recognize the difference between a Novell volume and a non-Novell volume with the same name, the duplicate names may be confusing for users of the catalog and is generally not recommended.
Macintosh systems identify volumes by creation date, based on the Macintosh's internal clock. It is important that when multiple users are accessing the same Fetch catalog, they all have their Macintosh internal clocks accurately synchronized. Otherwise, Fetch may consider the same volume as two different volumes and catalog the same files more than once.
The default memory allocation (2400K) for Fetch is based on average file sizes and systems. Cataloging very large images may require an allocation of 3 MB or higher.
When saving EPS files that you plan to catalog in Fetch, you must save a PICT preview even if you also save a pnot preview with the file. Otherwise, you cannot preview the image in Fetch or copy and paste it into another application.
-- Excluding a file from adding or updating
The exclusions file can contain a maximum of 800 filenames. If you try to add additional names, you hear a beep rather than see an alert or other message.
-- Using Aldus Fetch on a network
For additional information and recommended procedures, see the separate file, ReadMe (Networks).
